|
|
|
|
|
|
|
Saving and displaying test logs |
|
|
|
|
|
|
|
|
Using source code control with emphasis on SourceSafe |
|
|
|
|
|
|
|
|
Local directory structuring |
|
|
|
|
|
|
|
|
The Samsona Bank Teller System Example |
|
|
|
|
|
|
|
|
Understanding the Theory Behind the Self-Testing Object |
|
|
|
|
|
|
|
|
Testing and quality assurance are important activities for any object-oriented programming project. Gone are the days when ignoring these aspects of effective development was basically accepted. Today's technology is far more complex and demanding than previous technological paradigms, meaning that serious flaws and potentially critical mishaps must be addressed at every level of an application's design. |
|
|
|
|
|
|
|
|
Self-testing involves creating tests during the design phase that you then build into classes. During class or unit testing, you or a peer developer invokes these methods, noting preconditions, invariants, and postconditions. During application testing, a tester will indirectly invoke these methods, upon which the test class will store the results of the test for its responsibilities in a log file or display the results on the screen. |
|
|
|
|
|
|
|
|
Testers will need to test not only the application, but the user documentation and design model logic as well. This means that testers will face increasing pressure to ensure quality at as many checkpoints and milestones in a project as possible. Of course, as a crack programmer and designer, you can do your part to make sure that your class testing (unit testing) efforts are effective. Thus, classes and subsystems of packages will need to be designed and programmed to test themselvesthat is, test their own publicly visible behavior. |
|
|
|
|
|
|
|
|
Before you build in the testing features that your Visual Basic classes and subsystems need, you should be familiar with testing activities in general. With a heightened sense of appreciation for the testing process, your implementation of self-testing facilities should be of increased quality. |
|
|
|
|
|
|
|
|
As a programmer, you have been involved in code and design inspections, code reviews, or code and design walkthroughs. Inspections give a chance for your peers and architects to review your code and design models, praise the good parts, and offer constructive criticism of any discovered flaws. |
|
|
|
|
|